Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-251671 | SPLK-CL-000180 | SV-251671r808249_rule | Low |
Description |
---|
If the system were to continue processing after audit failure, actions could be taken on the system that could not be tracked and recorded for later forensic analysis. To perform this function, some type of heartbeat configuration with all of the devices and hosts must be configured. |
STIG | Date |
---|---|
Splunk Enterprise 8.x for Linux Security Technical Implementation Guide | 2022-06-07 |
Check Text ( C-55109r808247_chk ) |
---|
If the Splunk instance is used for Tier 2 CSSP (formerly CND-SP) or JRSS analysis, this check is N/A. Interview the SA to verify that a report exists to notify the SA and ISSO of any audit failure, such as loss of communication or logs no longer being collected. Interview the ISSO to confirm receipt of this report. If a report does not exist to notify the SA and ISSO of audit failure events, or the ISSO does not confirm receipt of this report, this is a finding. |
Fix Text (F-55063r808248_fix) |
---|
If the Splunk instance is used for Tier 2 CSSP (formerly CND-SP) or JRSS analysis, this check is N/A. Configure Splunk Enterprise, using the reporting and notification tools, to create a report with notification to the SA and ISSO of any audit failure events, such as loss of communication or logs no longer being collected. |